Systems and methods for providing backup interfaces

ABSTRACT

A computer-implemented method for providing backup interfaces may include (1) identifying a backup policy configured to back up a source system according to a backup configuration, (2) identifying a request to display the backup policy within a graphical user interface, and in response to the request, (3) portraying the backup policy within the graphical user interface as a flow diagram, the flow diagram including (i) a first box representing the source system, the first box displaying an identifier of the source system, (ii) a second box representing a backup stage of the backup policy, the second box displaying an identifier of the backup stage, and (iii) a directed edge connecting the first box and the second box, the directed edge indicating a sequence beginning with the first box and progressing to the second box. Various other methods, systems, and computer-readable media are also disclosed.

BACKGROUND

In the digital age, organizations increasingly rely on digitally-storeddata. To protect against data loss, an organization may use one or morebackup systems to back up important data.

Due to increasingly complex information technology infrastructures, anorganization may create backups from a variety of sources, using avariety of methods, and according to a variety of different schedules.In some cases, an organization may create a backup as a part of a largermulti-stage backup process, where the backup may in turn be duplicated,virtualized, archived, etc. Furthermore, one or more of these backupstages may occur in parallel with other backup stages.

Unfortunately, managing complex multi-stage backups using traditionalbackup systems may be difficult and time-consuming for an administrator.For example, the administrator may have to navigate back and forththrough various windows, tabs, and/or menus of a graphical interface toconfigure each stage of the larger scheme. Furthermore, theadministrator may have to ensure various configuration parameters ofconsecutive stages match and/or are compatible. Even after the time andeffort spent by an administrator, the confusion and discontinuitiescaused by using a traditional backup system to configure a complexmulti-stage backup operation may result in human error. Accordingly, theinstant disclosure identifies and addresses a need for additional andimproved systems and methods for providing backup interfaces.

SUMMARY

As will be described in greater detail below, the instant disclosuregenerally relates to systems and methods for providing backup interfacesby displaying multi-stage backup policies in flow diagrams and, in someexamples, allowing users to dynamically edit the backup policies via theflow diagrams (e.g., by adding and/or removing backup stages from theflow diagrams and/or editing configuration details within the backupstages of the flow diagrams). In one example, a computer-implementedmethod for providing backup interfaces may include (1) identifying abackup policy configured to back up a source system according to abackup configuration, (2) identifying a request to display the backuppolicy within a graphical user interface, and in response to therequest, (3) portraying the backup policy within the graphical userinterface as a flow diagram, the flow diagram including (i) a first boxrepresenting the source system, the first box displaying an identifierof the source system, (ii) a second box representing a backup stage ofthe backup policy, the second box displaying an identifier of the backupstage, and (iii) a directed edge connecting the first box and the secondbox, the directed edge indicating a sequence beginning with the firstbox and progressing to the second box.

In some examples, the first box may also display at least one identifiedselection of data to back up from the source system according to thebackup policy. Additionally or alternatively, the first box may includeat least one interface element for modifying a selection of data to backup from the source system within the backup policy within the first box.

In some examples, the second box may also display at least oneconfiguration detail of the backup stage within the backup policy, theconfiguration detail including a storage target of the backup stageand/or a schedule of the backup stage. Additionally or alternatively,the second box may include at least one interface element for modifyingat least one configuration detail of the backup stage within the secondbox. In some examples, the second box may include an interface elementfor adding an additional backup stage to the backup policy, theadditional backup stage being applied to data created at the backupstage. In these examples, the computer-implemented method may alsoinclude (1) receiving an input via the interface element and, inresponse to the input, (2) adding the additional backup stage to thebackup policy and (3) modifying the flow diagram to include (i) a thirdbox representing the additional backup stage and (ii) an additionaldirected edge connecting the second box and the third box, theadditional directed edge indicating a sequence beginning with the secondbox and progressing to the third box; and (4) displaying the modifiedflow diagram within the graphical user interface.

In some embodiments, the directed edge may include an arrow pointingfrom the first box to the second box. In some examples, the flow diagrammay also include (1) a third box representing an additional backup stageof the backup policy, the additional backup stage being applied to thesource system and (2) an additional directed edge connecting the firstbox and the third box, the additional directed edge indicating asequence beginning with the first box and progressing to the third box.Additionally or alternatively, the flow diagram may also include (1) athird box representing an additional backup stage of the backup policy,the additional backup stage being applied to data created at the backupstage and (2) an additional directed edge connecting the second box andthe third box, the additional directed edge indicating a sequencebeginning with the second box and progressing to the third box.

In one embodiment, a system for implementing the above-described methodmay include an identification module programmed to (1) identify a backuppolicy configured to back up a source system according to a backupconfiguration and (2) identify a request to display the backup policywithin a graphical user interface. The system may also include aninterface module programmed to, in response to the request, portray thebackup policy within the graphical user interface as a flow diagram, theflow diagram including (1) a first box representing the source system,the first box displaying an identifier of the source system, (2) asecond box representing a backup stage of the backup policy, the secondbox displaying an identifier of the backup stage, and (3) a directededge connecting the first box and the second box, the directed edgeindicating a sequence beginning with the first box and progressing tothe second box. The system may additionally include at least oneprocessor configured to execute the identification module and theinterface module.

In some examples, the above-described method may be encoded ascomputer-readable instructions on a computer-readable-storage medium.For example, a computer-readable-storage medium may include one or morecomputer-executable instructions that, when executed by at least oneprocessor of a computing device, may cause the computing device to (1)identify a backup policy configured to back up a source system accordingto a backup configuration, (2) identify a request to display the backuppolicy within a graphical user interface, and in response to therequest, (3) portray the backup policy within the graphical userinterface as a flow diagram, the flow diagram including (i) a first boxrepresenting the source system, the first box displaying an identifierof the source system, (ii) a second box representing a backup stage ofthe backup policy, the second box displaying an identifier of the backupstage, and (iii) a directed edge connecting the first box and the secondbox, the directed edge indicating a sequence beginning with the firstbox and progressing to the second box.

As will be explained in greater detail below, by displaying multi-stagebackup policies in flow diagrams, the systems and methods describedherein may enable an administrator to view one or more stages of abackup policy at once in a visually organized manner. Furthermore, insome examples, by allowing administrators to dynamically edit the backuppolicies via the flow diagrams (e.g., by adding and/or removing backupstages from the flow diagrams and/or editing configuration detailswithin the backup stages of the flow diagrams), these systems andmethods may reduce the time and effort that may otherwise be spent innavigating back and forth through a backup system graphical userinterface and may also thereby reduce human error involved in creating,modifying, and/or assessing the state of backup policies.

Features from any of the above-mentioned embodiments may be used incombination with one another in accordance with the general principlesdescribed herein. These and other embodiments, features, and advantageswill be more fully understood upon reading the following detaileddescription in conjunction with the accompanying drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrate a number of exemplary embodimentsand are a part of the specification. Together with the followingdescription, these drawings demonstrate and explain various principlesof the instant disclosure.

FIG. 1 is a block diagram of an exemplary system for providing backupinterfaces.

FIG. 2 is a block diagram of an exemplary system for providing backupinterfaces.

FIG. 3 is a flow diagram of an exemplary method for providing backupinterfaces.

FIG. 4 is a diagram of an exemplary graphical user interface forproviding backup interfaces.

FIG. 5 is a diagram of an exemplary graphical user interface forproviding backup interfaces.

FIG. 6 is a diagram of an exemplary graphical user interface forproviding backup interfaces.

FIG. 7 is a diagram of an exemplary graphical user interface forproviding backup interfaces.

FIG. 8 is a diagram of an exemplary graphical user interface forproviding backup interfaces.

FIG. 9 is a block diagram of an exemplary computing system capable ofimplementing one or more of the embodiments described and/or illustratedherein.

FIG. 10 is a block diagram of an exemplary computing network capable ofimplementing one or more of the embodiments described and/or illustratedherein.

Throughout the drawings, identical reference characters and descriptionsindicate similar, but not necessarily identical, elements. While theexemplary embodiments described herein are susceptible to variousmodifications and alternative forms, specific embodiments have beenshown by way of example in the drawings and will be described in detailherein. However, the exemplary embodiments described herein are notintended to be limited to the particular forms disclosed. Rather, theinstant disclosure covers all modifications, equivalents, andalternatives falling within the scope of the appended claims.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

The following will provide, with reference to FIGS. 1-2, detaileddescriptions of exemplary systems for providing backup interfaces.Detailed descriptions of corresponding computer-implemented methods willalso be provided in connection with FIG. 3. Detailed descriptions ofexemplary graphical user interfaces will be provided in connection withFIGS. 4-8. In addition, detailed descriptions of an exemplary computingsystem and network architecture capable of implementing one or more ofthe embodiments described herein will be provided in connection withFIGS. 9 and 10, respectively.

FIG. 1 is a block diagram of an exemplary system 100 for providingbackup interfaces. As illustrated in this figure, exemplary system 100may include one or more modules 102 for performing one or more tasks.For example, and as will be explained in greater detail below, exemplarysystem 100 may include an identification module 104 programmed to (1)identify a backup policy configured to back up a source system accordingto a backup configuration and (2) identify a request to display thebackup policy within a graphical user interface.

In addition, and as will be described in greater detail below, exemplarysystem 100 may include an interface module 106 programmed to, inresponse to the request, portray the backup policy within the graphicaluser interface as a flow diagram, the flow diagram including (1) a firstbox representing the source system, the first box displaying anidentifier of the source system, (2) a second box representing a backupstage of the backup policy, the second box displaying an identifier ofthe backup stage, and (3) a directed edge connecting the first box andthe second box, the directed edge indicating a sequence beginning withthe first box and progressing to the second box. Although illustrated asseparate elements, one or more of modules 102 in FIG. 1 may representportions of a single module or application.

In certain embodiments, one or more of modules 102 in FIG. 1 mayrepresent one or more software applications or programs that, whenexecuted by a computing device, may cause the computing device toperform one or more tasks. For example, and as will be described ingreater detail below, one or more of modules 102 may represent softwaremodules stored and configured to run on one or more computing devices,such as the devices illustrated in FIG. 2 (e.g., computing device 202,servers 206(1)-(n), and/or backup storage devices 208(1)-(m)), computingsystem 910 in FIG. 9, and/or portions of exemplary network architecture1000 in FIG. 10. One or more of modules 102 in FIG. 1 may also representall or portions of one or more special-purpose computers configured toperform one or more tasks.

Exemplary system 100 in FIG. 1 may be implemented in a variety of ways.For example, all or a portion of exemplary system 100 may representportions of exemplary system 200 in FIG. 2. As shown in FIG. 2, system200 may include a computing device 202 in communication with servers206(1)-(n) and backup storage devices 208(1)-(m) via a network 204. Forexample, computing device 202 may represent a backup centraladministration server used to configure backup policies for backing updata from one or more of servers 206(1)-(n) to one or more of storagedevices 208(1)-(m).

In one embodiment, one or more of modules 102 from FIG. 1 may, whenexecuted by at least one processor of computing device 202, facilitatecomputing device 202 in providing backup interfaces. For example, and aswill be described in greater detail below, one or more of modules 102may cause computing device 202 to (1) identify a backup policy (e.g., abackup policy 210) configured to back up a source system (e.g., server206(1)) according to a backup configuration, (2) identify a request(e.g., a request 212) to display the backup policy within a graphicaluser interface (e.g., a graphical user interface 220), and in responseto the request, (3) portray the backup policy within the graphical userinterface as a flow diagram (e.g., portray backup policy 210 withingraphical user interface 220 as a flow diagram 222), the flow diagramincluding (i) a first box representing the source system, the first boxdisplaying an identifier of the source system, (ii) a second boxrepresenting a backup stage of the backup policy, the second boxdisplaying an identifier of the backup stage, and (iii) a directed edgeconnecting the first box and the second box, the directed edgeindicating a sequence beginning with the first box and progressing tothe second box.

Computing device 202 generally represents any type or form of computingdevice capable of reading computer-executable instructions. Examples ofcomputing device 202 include, without limitation, laptops, desktops,servers, cellular phones, personal digital assistants (PDAs), multimediaplayers, embedded systems, combinations of one or more of the same,exemplary computing system 910 in FIG. 9, or any other suitablecomputing device.

Servers 206(1)-(n) generally represent any type or form of computingdevices that are capable of storing, managing, and/or processing data.Examples of servers 206(1)-(n) include, without limitation, applicationservers and database servers configured to provide various databaseservices and/or run certain software applications.

Network 204 generally represents any medium or architecture capable offacilitating communication or data transfer. Examples of network 204include, without limitation, an intranet, a wide area network (WAN), alocal area network (LAN), a storage area network (SAN), a personal areanetwork (PAN), the Internet, power line communications (PLC), a cellularnetwork (e.g., a GSM Network), exemplary network architecture 1000 inFIG. 10, or the like. Network 204 may facilitate communication or datatransfer using wireless or wired connections. In one embodiment, network204 may facilitate communication between computing device 202 and server206.

Backup storage devices 208(1)-(m) may each represent portions ofindividual databases or storage devices or of pluralities of databasesor storage devices. For example, one or more of backup storage devices208(1)-(m) may represent a portion of servers 206(1)-(n) in FIG. 2,computing system 910 in FIG. 9, and/or portions of exemplary networkarchitecture 1000 in FIG. 10. Alternatively, backup storage devices208(1)-(m) in FIG. 1 may represent one or more physically separatedevices capable of being accessed by a computing device, such as servers206(1)-(n) in FIG. 2, computing system 910 in FIG. 9, and/or portions ofexemplary network architecture 1000 in FIG. 10.

FIG. 3 is a flow diagram of an exemplary computer-implemented method 300for providing backup interfaces. The steps shown in FIG. 3 may beperformed by any suitable computer-executable code and/or computingsystem. In some embodiments, the steps shown in FIG. 3 may be performedby one or more of the components of system 100 in FIG. 1, system 200 inFIG. 2, computing system 910 in FIG. 9, and/or portions of exemplarynetwork architecture 1000 in FIG. 10.

As illustrated in FIG. 3, at step 302 one or more of the systemsdescribed herein may identify a backup policy configured to back up asource system according to a backup configuration. For example, at step302 identification module 104 may, as part of computing device 202 inFIG. 2, identify backup policy 210 configured to back up server 206(1).

As used herein, the phrase “backup policy” may refer to any collectionof configurations, scripts, jobs, and/or specifications for performingone or more backup operations. As used herein, the phrase “backupoperation” may include any operation for backing up, protecting,transferring, and/or replicating data. Examples of backup operationsinclude, without limitation, backing up data (e.g., to a disk, a tape, adeduplication data store, etc.), duplicating data (e.g., to a disk, atape, etc.), archiving data, migrating data, creating a virtual copy ofa system, etc. As used herein, the phrase “source system” may refer toany system from which data is retrieved and/or for which data isprotected in a backup operation.

Identification module 104 may identify the backup policy in any of avariety of contexts. For example, identification module 104 may identifythe backup policy by receiving input from a graphical user interfaceselecting the backup policy. Additionally or alternatively,identification module 104 may identify the backup policy by receivinginput from a graphical user interface selecting a system implicated inthe backup policy (e.g., the source system). In some examples,identification module 104 may identify the backup policy after thebackup policy has been created and/or while the backup policy is ineffect. Additionally or alternatively, identification module 104 mayidentify the backup policy when the backup policy is first created(e.g., by creating the backup policy) and/or while the backup policy isstill tentative.

FIG. 4 is an illustration of an exemplary graphical user interface 400.Using FIG. 4 as an example, graphical user interface 400 may allow anadministrator to select a server for backup. As shown in FIG. 4, anadministrator may make a selection 410 of a server for backup (e.g., asource system). In some examples, the administrator may then interactwith an interface element 420 (by, e.g., clicking a backup button forconfiguring a backup for the server selected in selection 410).

FIG. 5 is an illustration of an exemplary graphical user interface 500.As shown in FIG. 5, graphical user interface 500 may provide a pull-downmenu (e.g., after the administrator interacted with interface element420 in FIG. 4) to select an initial backup configuration for the backuppolicy. In some examples, the administrator may select a selection 510(e.g., to back up the server to disk). Using FIGS. 4 and 5 as anexample, at step 302 identification 104 may identify the backup policyconfigured to back up the source system according to the backupconfiguration by identifying a tentative backup policy created byselecting selection 410 (e.g., to select the source system) andselecting selection 510 (e.g., to select the backup configuration forthe backup policy).

Returning to FIG. 3, at step 304 one or more of the systems describedherein may identify a request to display the backup policy within agraphical user interface. For example, at step 304 identification module104 may, as part of computing device 202 in FIG. 2, identify request 212to display backup policy 210 within graphical user interface 220.

As used herein, the phrase “graphical user interface” may refer to anyinterface that may allow a user to interact with a computing system. Insome examples, the graphical user interface may include an interface fora backup central administration server.

Identification module 104 may identify the request in any of a varietyof contexts. For example, identification module 104 may identify therequest by receiving a communication from and/or within the graphicaluser interface that the backup policy has been selected. Additionally oralternatively, identification module 104 may identify the request byreceiving a communication from and/or within the graphical userinterface that a system implicated in the backup policy (e.g., thesource system) has been selected. Using FIG. 5 as an example, byselecting selection 510 an administrator may generate a request tocreate a tentative backup policy and to display the tentative backuppolicy.

Returning to FIG. 3, at step 306 one or more of the systems describedherein may portray the backup policy within the graphical user interfaceas a flow diagram. The flow diagram may include (1) a first boxrepresenting the source system, the first box displaying an identifierof the source system, (2) a second box representing a backup stage ofthe backup policy, the second box displaying an identifier of the backupstage, and (3) a directed edge connecting the first box and the secondbox, the directed edge indicating a sequence beginning with the firstbox and progressing to the second box. For example, at step 306interface module 106 may, as part of computing device 202 in FIG. 2,portray backup policy 210 within graphical user interface 220 as a flowdiagram 222.

As used herein, the phrase “flow diagram” may refer to any diagramand/or illustration of one or more interconnected elements. In someexamples, the flow diagram may illustrate a sequence and/or one or moredependencies between the interconnected elements.

As used herein, the term “box” may refer to any distinct element of aflow diagram. In some examples, the term “box” may refer to arectilinear and/or rectangular figure within a flow diagram.Additionally or alternatively, the term “box” may refer to a vertex,node, and/or interconnection point within the flow diagram. In someexamples, the term “box” may refer to a figure with a distinct outline.Alternatively, the term “box” may refer to an area otherwise portrayedas distinct, whether by coloring, by shading, by clustering of elementswithin the box, by the distance of the box from one or more other boxes,by one or more elements (e.g., edges connecting to the box) interveningbetween the box and one or more other boxes, and/or by the alignment ofthe box within the flow diagram and/or with respect to one or more otherelements within the flow diagram.

The identifier of the source system may include any of a variety ofinformation. In some examples, the identifier of the source system mayinclude a name of the source system. Additionally or alternatively, theidentifier of the source system may include an icon representing thesource system (e.g., according to one or more characteristics of thesource system). In some examples, the identifier may include a networkaddress of the source system.

The first box may include any of a variety of elements and/orinformation. For example, the first box may display at least oneidentified selection of data to back up from the source system accordingto the backup policy. For example, the first box may display one or morevolumes selected for backup (in full or in part), state information ofthe source system selected for backup, database instances selected forbackup, etc. In some examples, the first box may also display what dataof the source system has not been selected for backup according to thebackup policy.

FIG. 6 is an illustration of an exemplary graphical user interface 600.As shown in FIG. 6, graphical user interface 600 may include a box 610.Using FIG. 6 as an example, box 610 may include configuration details670. In one example, configuration details 670 may show that the wholeof a volume “C:” has been selected for backup, that the state of thesource system has been selected for backup, and that elements of avolume “E:” have been selected for backup. Configuration details 670 mayalso show that one or more database instances associated with the sourcesystem have not been selected for backup.

In some examples, the first box may also include at least one interfaceelement for modifying a selection of data to back up from the sourcesystem within the backup policy within the first box. As used herein,the phrase “interface element” may refer to any element which maytrigger an action within an interface and/or which may allow editingwithin an interface. For example, the interface element may include abutton configured to open a configuration editor. Additionally oralternatively, the interface element may include a button for unlockinginline editing of the selection of data (e.g., enabling the manipulationof one or more interface elements used to display the data selected forbackup). In some examples, the interface element may include aninterface element used to display the data selected for backup (e.g., atext box, a pull-down menu, a checkbox, a radio button, etc.). UsingFIG. 6 as an example, graphical user interface 600 may include aninterface element 640 (e.g., an “edit” button) for modifying theselection of data (e.g., configuration details 670) to back up from thesource system.

As used herein, the phrase “backup stage” may refer to any stage withina backup policy at which a backup operation (e.g., as described above)is performed. For example, a backup stage may include backing up data(e.g., to a disk, a tape, a deduplication data store, etc.), duplicatingdata (e.g., to a disk, a tape, etc.), archiving data, migrating data,creating a virtual copy of a system, etc. The identifier of the backupstage may include any of a variety of information. In some examples, theidentifier of the backup stage may include a name of a backup operationperformed at the backup stage. Additionally or alternatively, theidentifier of the backup stage may include an icon representing thebackup operation performed at the backup stage. Using FIG. 6 as anexample, graphical user interface 600 may include a box 620. As shown inFIG. 6, box 620 may include an icon and text identifying box 620 asrepresenting a backup.

In some examples, the second box may also display at least oneconfiguration detail of the backup stage within the backup policy. Forexample, the configuration detail may include a storage target of thebackup stage and/or a schedule of the backup stage. In this example, thestorage target may identify and/or represent a location at which thedata retrieved from the source system for a backup operation definedwithin the backup policy (e.g., and represented by the second box) willbe stored. Likewise, the schedule may identify and/or represent one ormore times (e.g., defined by times specified on an individual and/orperiodic basis and/or defined by one or more events) at which a backupoperation corresponding to the backup stage represented by the secondbox will occur. In some examples, the configuration detail may alsoinclude an expiration of backup data generated at the backup stage.Using FIG. 6 as an example, box 620 may include configuration details680. As shown in FIG. 6, configuration details 680 may specify that thebackup stage represented by box 620 may include a recurring weekly fullbackup that uses any available disk storage and is preserved for fourweeks. Configuration details 680 may also specify that the backup stagerepresented by box 620 may include a recurring daily backup that usesany available disk storage and is preserved for four weeks.

In some examples, the second box may include at least one interfaceelement for modifying at least one configuration detail of the backupstage within the second box. Using FIG. 6 as an example, box 620 mayinclude an interface element 650 (e.g., an edit button) to enable theediting of configuration details 680 (e.g., inline or in a separatewindow).

As used herein, the phrase “directed edge” may refer to any edge,connector, pointer, and/or visual representation of a flow, transition,and/or relationship between boxes. For example, the directed edge mayinclude an arrow pointing from the first box to the second box. In someexamples, the directed edge may include a distinct graphic and/or icon.Additionally or alternatively, the directed edge may include a visualindicator formed by negative space and/or alignment of two or moreboxes. For example, the directed edge may include an implicit connectionand flow between two boxes that are horizontally or vertically alignedbut have no intervening icons. In this example, the directed edge mayindicate the sequence based on the relative positions of the boxes basedon convention. For example, two boxes may be horizontally aligned andthe directed edge may include the horizontal alignment. In this case,the horizontal alignment may indicate a sequence beginning with theleft-side box and progressing to the right-side box. Alternatively, twoboxes may be vertically aligned and the directed edge may include thevertical alignment. In this case, the vertical alignment may indicate asequence beginning with the upper box and progressing to the lower box.Using FIG. 6 as an example, graphical user interface 600 may include adirected edge 630 (e.g., an arrow) connecting box 610 and box 620 andindicating a sequence beginning with box 610 and progressing to box 620.

In some examples, the second box may include an interface element foradding an additional backup stage to the backup policy, the additionalbackup stage being applied to data created at the backup stage. UsingFIG. 6 as an example, box 620 may include an interface element 660(e.g., a button-based pull-down menu) for adding an additional backupstage to the backup policy that depends on the backup stage representedby box 620.

In some examples, one or more systems described herein (e.g., interfacemodule 106) may handle input to the interface element for adding theadditional backup stage. For example, interface module 106 may receivean input via the interface element. Interface module 106 may then, inresponse to the input, add the additional backup stage to the backuppolicy. Interface module 106 may also modify the flow diagram to includea third box representing an additional backup stage of the backuppolicy, the additional backup stage being applied to data created at thebackup stage. Interface module 106 may additionally modify the flowdiagram to include an additional directed edge connecting the second boxand the third box, the additional directed edge indicating a sequencebeginning with the second box and progressing to the third box.Interface module may also display the modified flow diagram within thegraphical user interface.

FIG. 7 is an illustration of an exemplary graphical user interface 700.As shown in FIG. 7, graphical user interface 700 may include box 610 andbox 620 from FIG. 6. Graphical user interface 700 may also include a box710. Box 710 may have been created by an administrator using interfaceelement 660 to select a new backup stage (e.g., a duplication operation)to depend from box 620. Accordingly, the backup policy may, asrepresented by graphical user interface 700, now include a backupperformed from the source system and a duplication performed from thebackup.

In some examples, by creating and/or modifying a backup stage, interfacemodule 106 may also automatically modify the configuration of relatedbackup stages. For example, an administrator may modify box 620 tospecify a particular storage device for the full backup. Interfacemodule 106 may then automatically modify the source of the duplicationoperation represented in box 710 to duplicate from the specified source.By automatically configuring portions of a backup stage based on changesto a related backup stage, the systems and methods described herein maymake modifications to backup policies more intuitive and more efficientwhile reducing chances for human error. Furthermore, by allowing anadministrator to specify elements of backup configuration at a logicallevel (e.g., specifying storage as “any disk storage,”), these systemsand methods may use the high-level configuration decisions of theadministrator to automatically populate underlying configuration detailsof one or more backup stages.

In some examples, the flow diagram may also include a third boxrepresenting an additional backup stage of the backup policy, theadditional backup stage being applied to the source system and anadditional directed edge connecting the first box and the third box, theadditional directed edge indicating a sequence beginning with the firstbox and progressing to the third box. For example, the backup policy maybe configured to backup and archive the same data from the sourcesystem. Accordingly, the flow diagram may show both a backup stageimplementing a backup and a backup stage implementing an archiveoperation depending on the source system.

In some examples, the flow diagram may also include a third boxrepresenting an additional backup stage of the backup policy, theadditional backup stage being applied to data created at the backupstage and an additional directed edge connecting the second box and thethird box, the additional directed edge indicating a sequence beginningwith the second box and progressing to the third box.

FIG. 8 is an illustration of an exemplary graphical user interface 800.As shown in FIG. 8, graphical user interface 800 may include box 610 andbox 620 from FIG. 6, box 710 from FIG. 7, and a box 810. Both box 710and box 810 may depend on box 620. For example, the data backed up by abackup operation at a stage represented by box 620 may be used both forduplication as shown by box 710 and may be stored in a virtual machineas shown in box 810.

While the illustrations discussed herein may show backup policies withthree or four stages, the backup policy may include any number of stagesand the flow diagram may include any number of boxes to represent thestages. Using FIG. 8 as an example, an administrator may add anarchiving stage depending on box 610. Additionally or alternatively, theadministrator may add another duplication stage following box 710.

In some examples, interface module 106 may create the flow diagramwithin the graphical user interface to allow an administrator to drag abox from depending on one box to depending on another box. In thismanner an administrator may dynamically manipulate ordering anddependencies within the flow diagram. In some examples, an administratormay delete a box using one or more interface elements. In at least oneexample, by deleting a box from the flow diagram, each box following thebox may also be deleted. In some examples, these changes may alter thebackup policy to reflect the new state of the flow diagram. In someexamples, changes to the backup policy may be instantly made accordingto changes in the flow diagram. Additionally or alternatively, changesto the backup policy may be committed using an interface element withinthe graphical user interface.

As explained above, by displaying multi-stage backup policies in flowdiagrams, the systems and methods described herein may enable anadministrator to view one or more stages of a backup policy at once in avisually organized manner. Furthermore, in some examples, by allowingadministrators to dynamically edit the backup policies via the flowdiagrams (e.g., by adding and/or removing backup stages from the flowdiagrams and/or editing configuration details within the backup stagesof the flow diagrams), these systems and methods may reduce the time andeffort that may otherwise be spent in navigating back and forth througha backup system graphical user interface and may also thereby reducehuman error involved in creating, modifying, and/or assessing the stateof backup policies.

FIG. 9 is a block diagram of an exemplary computing system 910 capableof implementing one or more of the embodiments described and/orillustrated herein. For example, all or a portion of computing system910 may perform and/or be a means for performing, either alone or incombination with other elements, one or more of the identifying,portraying, displaying, representing, receiving, adding, modifying, andconnecting steps described herein. All or a portion of computing system910 may also perform and/or be a means for performing any other steps,methods, or processes described and/or illustrated herein.

Computing system 910 broadly represents any single or multi-processorcomputing device or system capable of executing computer-readableinstructions. Examples of computing system 910 include, withoutlimitation, workstations, laptops, client-side terminals, servers,distributed computing systems, handheld devices, or any other computingsystem or device. In its most basic configuration, computing system 910may include at least one processor 914 and a system memory 916.

Processor 914 generally represents any type or form of processing unitcapable of processing data or interpreting and executing instructions.In certain embodiments, processor 914 may receive instructions from asoftware application or module. These instructions may cause processor914 to perform the functions of one or more of the exemplary embodimentsdescribed and/or illustrated herein.

System memory 916 generally represents any type or form of volatile ornon-volatile storage device or medium capable of storing data and/orother computer-readable instructions. Examples of system memory 916include, without limitation, random access memory (RAM), read onlymemory (ROM), flash memory, or any other suitable memory device.Although not required, in certain embodiments computing system 910 mayinclude both a volatile memory unit (such as, for example, system memory916) and a non-volatile storage device (such as, for example, primarystorage device 932, as described in detail below). In one example, oneor more of modules 102 from FIG. 1 may be loaded into system memory 916.

In certain embodiments, exemplary computing system 910 may also includeone or more components or elements in addition to processor 914 andsystem memory 916. For example, as illustrated in FIG. 9, computingsystem 910 may include a memory controller 918, an Input/Output (I/O)controller 920, and a communication interface 922, each of which may beinterconnected via a communication infrastructure 912. Communicationinfrastructure 912 generally represents any type or form ofinfrastructure capable of facilitating communication between one or morecomponents of a computing device. Examples of communicationinfrastructure 912 include, without limitation, a communication bus(such as an ISA, PCI, PCIe, or similar bus) and a network.

Memory controller 918 generally represents any type or form of devicecapable of handling memory or data or controlling communication betweenone or more components of computing system 910. For example, in certainembodiments memory controller 918 may control communication betweenprocessor 914, system memory 916, and I/O controller 920 viacommunication infrastructure 912.

I/O controller 920 generally represents any type or form of modulecapable of coordinating and/or controlling the input and outputfunctions of a computing device. For example, in certain embodiments I/Ocontroller 920 may control or facilitate transfer of data between one ormore elements of computing system 910, such as processor 914, systemmemory 916, communication interface 922, display adapter 926, inputinterface 930, and storage interface 934.

Communication interface 922 broadly represents any type or form ofcommunication device or adapter capable of facilitating communicationbetween exemplary computing system 910 and one or more additionaldevices. For example, in certain embodiments communication interface 922may facilitate communication between computing system 910 and a privateor public network including additional computing systems. Examples ofcommunication interface 922 include, without limitation, a wired networkinterface (such as a network interface card), a wireless networkinterface (such as a wireless network interface card), a modem, and anyother suitable interface. In at least one embodiment, communicationinterface 922 may provide a direct connection to a remote server via adirect link to a network, such as the Internet. Communication interface922 may also indirectly provide such a connection through, for example,a local area network (such as an Ethernet network), a personal areanetwork, a telephone or cable network, a cellular telephone connection,a satellite data connection, or any other suitable connection.

In certain embodiments, communication interface 922 may also represent ahost adapter configured to facilitate communication between computingsystem 910 and one or more additional network or storage devices via anexternal bus or communications channel. Examples of host adaptersinclude, without limitation, SCSI host adapters, USB host adapters, IEEE1394 host adapters, SATA and eSATA host adapters, ATA and PATA hostadapters, Fibre Channel interface adapters, Ethernet adapters, or thelike. Communication interface 922 may also allow computing system 910 toengage in distributed or remote computing. For example, communicationinterface 922 may receive instructions from a remote device or sendinstructions to a remote device for execution.

As illustrated in FIG. 9, computing system 910 may also include at leastone display device 924 coupled to communication infrastructure 912 via adisplay adapter 926. Display device 924 generally represents any type orform of device capable of visually displaying information forwarded bydisplay adapter 926. Similarly, display adapter 926 generally representsany type or form of device configured to forward graphics, text, andother data from communication infrastructure 912 (or from a framebuffer, as known in the art) for display on display device 924.

As illustrated in FIG. 9, exemplary computing system 910 may alsoinclude at least one input device 928 coupled to communicationinfrastructure 912 via an input interface 930. Input device 928generally represents any type or form of input device capable ofproviding input, either computer or human generated, to exemplarycomputing system 910. Examples of input device 928 include, withoutlimitation, a keyboard, a pointing device, a speech recognition device,or any other input device.

As illustrated in FIG. 9, exemplary computing system 910 may alsoinclude a primary storage device 932 and a backup storage device 933coupled to communication infrastructure 912 via a storage interface 934.Storage devices 932 and 933 generally represent any type or form ofstorage device or medium capable of storing data and/or othercomputer-readable instructions. For example, storage devices 932 and 933may be a magnetic disk drive (e.g., a so-called hard drive), a solidstate drive, a floppy disk drive, a magnetic tape drive, an optical diskdrive, a flash drive, or the like. Storage interface 934 generallyrepresents any type or form of interface or device for transferring databetween storage devices 932 and 933 and other components of computingsystem 910.

In certain embodiments, storage devices 932 and 933 may be configured toread from and/or write to a removable storage unit configured to storecomputer software, data, or other computer-readable information.Examples of suitable removable storage units include, withoutlimitation, a floppy disk, a magnetic tape, an optical disk, a flashmemory device, or the like. Storage devices 932 and 933 may also includeother similar structures or devices for allowing computer software,data, or other computer-readable instructions to be loaded intocomputing system 910. For example, storage devices 932 and 933 may beconfigured to read and write software, data, or other computer-readableinformation. Storage devices 932 and 933 may also be a part of computingsystem 910 or may be a separate device accessed through other interfacesystems.

Many other devices or subsystems may be connected to computing system910. Conversely, all of the components and devices illustrated in FIG. 9need not be present to practice the embodiments described and/orillustrated herein. The devices and subsystems referenced above may alsobe interconnected in different ways from that shown in FIG. 9. Computingsystem 910 may also employ any number of software, firmware, and/orhardware configurations. For example, one or more of the exemplaryembodiments disclosed herein may be encoded as a computer program (alsoreferred to as computer software, software applications,computer-readable instructions, or computer control logic) on acomputer-readable-storage medium. The phrase “computer-readable-storagemedium” generally refers to any form of device, carrier, or mediumcapable of storing or carrying computer-readable instructions. Examplesof computer-readable-storage media include, without limitation,transmission-type media, such as carrier waves, and physical media, suchas magnetic-storage media (e.g., hard disk drives and floppy disks),optical-storage media (e.g., CD- or DVD-ROMs), electronic-storage media(e.g., solid-state drives and flash media), and other distributionsystems.

The computer-readable-storage medium containing the computer program maybe loaded into computing system 910. All or a portion of the computerprogram stored on the computer-readable-storage medium may then bestored in system memory 916 and/or various portions of storage devices932 and 933. When executed by processor 914, a computer program loadedinto computing system 910 may cause processor 914 to perform and/or be ameans for performing the functions of one or more of the exemplaryembodiments described and/or illustrated herein. Additionally oralternatively, one or more of the exemplary embodiments described and/orillustrated herein may be implemented in firmware and/or hardware. Forexample, computing system 910 may be configured as an applicationspecific integrated circuit (ASIC) adapted to implement one or more ofthe exemplary embodiments disclosed herein.

FIG. 10 is a block diagram of an exemplary network architecture 1000 inwhich client systems 1010, 1020, and 1030 and servers 1040 and 1045 maybe coupled to a network 1050. As detailed above, all or a portion ofnetwork architecture 1000 may perform and/or be a means for performing,either alone or in combination with other elements, one or more of theidentifying, portraying, displaying, representing, receiving, adding,modifying, and connecting steps disclosed herein. All or a portion ofnetwork architecture 1000 may also be used to perform and/or be a meansfor performing other steps and features set forth in the instantdisclosure.

Client systems 1010, 1020, and 1030 generally represent any type or formof computing device or system, such as exemplary computing system 910 inFIG. 9. Similarly, servers 1040 and 1045 generally represent computingdevices or systems, such as application servers or database servers,configured to provide various database services and/or run certainsoftware applications. Network 1050 generally represents anytelecommunication or computer network including, for example, anintranet, a wide area network (WAN), a local area network (LAN), apersonal area network (PAN), or the Internet. In one example, clientsystems 1010, 1020, and/or 1030 and/or servers 1040 and/or 1045 mayinclude all or a portion of system 100 from FIG. 1.

As illustrated in FIG. 10, one or more storage devices 1060(1)-(N) maybe directly attached to server 1040. Similarly, one or more storagedevices 1070(1)-(N) may be directly attached to server 1045. Storagedevices 1060(1)-(N) and storage devices 1070(1)-(N) generally representany type or form of storage device or medium capable of storing dataand/or other computer-readable instructions. In certain embodiments,storage devices 1060(1)-(N) and storage devices 1070(1)-(N) mayrepresent network-attached storage (NAS) devices configured tocommunicate with servers 1040 and 1045 using various protocols, such asNFS, SMB, or CIFS.

Servers 1040 and 1045 may also be connected to a storage area network(SAN) fabric 1080. SAN fabric 1080 generally represents any type or formof computer network or architecture capable of facilitatingcommunication between a plurality of storage devices. SAN fabric 1080may facilitate communication between servers 1040 and 1045 and aplurality of storage devices 1090(1)-(N) and/or an intelligent storagearray 1095. SAN fabric 1080 may also facilitate, via network 1050 andservers 1040 and 1045, communication between client systems 1010, 1020,and 1030 and storage devices 1090(1)-(N) and/or intelligent storagearray 1095 in such a manner that devices 1090(1)-(N) and array 1095appear as locally attached devices to client systems 1010, 1020, and1030. As with storage devices 1060(1)-(N) and storage devices1070(1)-(N), storage devices 1090(1)-(N) and intelligent storage array1095 generally represent any type or form of storage device or mediumcapable of storing data and/or other computer-readable instructions.

In certain embodiments, and with reference to exemplary computing system910 of FIG. 9, a communication interface, such as communicationinterface 922 in FIG. 9, may be used to provide connectivity betweeneach client system 1010, 1020, and 1030 and network 1050. Client systems1010, 1020, and 1030 may be able to access information on server 1040 or1045 using, for example, a web browser or other client software. Suchsoftware may allow client systems 1010, 1020, and 1030 to access datahosted by server 1040, server 1045, storage devices 1060(1)-(N), storagedevices 1070(1)-(N), storage devices 1090(1)-(N), or intelligent storagearray 1095. Although FIG. 10 depicts the use of a network (such as theInternet) for exchanging data, the embodiments described and/orillustrated herein are not limited to the Internet or any particularnetwork-based environment.

In at least one embodiment, all or a portion of one or more of theexemplary embodiments disclosed herein may be encoded as a computerprogram and loaded onto and executed by server 1040, server 1045,storage devices 1060(1)-(N), storage devices 1070(1)-(N), storagedevices 1090(1)-(N), intelligent storage array 1095, or any combinationthereof. All or a portion of one or more of the exemplary embodimentsdisclosed herein may also be encoded as a computer program, stored inserver 1040, run by server 1045, and distributed to client systems 1010,1020, and 1030 over network 1050.

As detailed above, computing system 910 and/or one or more components ofnetwork architecture 1000 may perform and/or be a means for performing,either alone or in combination with other elements, one or more steps ofan exemplary method for providing backup interfaces.

While the foregoing disclosure sets forth various embodiments usingspecific block diagrams, flowcharts, and examples, each block diagramcomponent, flowchart step, operation, and/or component described and/orillustrated herein may be implemented, individually and/or collectively,using a wide range of hardware, software, or firmware (or anycombination thereof) configurations. In addition, any disclosure ofcomponents contained within other components should be consideredexemplary in nature since many other architectures can be implemented toachieve the same functionality.

In some examples, all or a portion of exemplary system 100 in FIG. 1 mayrepresent portions of a cloud-computing or network-based environment.Cloud-computing environments may provide various services andapplications via the Internet. These cloud-based services (e.g.,software as a service, platform as a service, infrastructure as aservice, etc.) may be accessible through a web browser or other remoteinterface. Various functions described herein may be provided through aremote desktop environment or any other cloud-based computingenvironment.

The process parameters and sequence of steps described and/orillustrated herein are given by way of example only and can be varied asdesired. For example, while the steps illustrated and/or describedherein may be shown or discussed in a particular order, these steps donot necessarily need to be performed in the order illustrated ordiscussed. The various exemplary methods described and/or illustratedherein may also omit one or more of the steps described or illustratedherein or include additional steps in addition to those disclosed.

While various embodiments have been described and/or illustrated hereinin the context of fully functional computing systems, one or more ofthese exemplary embodiments may be distributed as a program product in avariety of forms, regardless of the particular type ofcomputer-readable-storage media used to actually carry out thedistribution. The embodiments disclosed herein may also be implementedusing software modules that perform certain tasks. These softwaremodules may include script, batch, or other executable files that may bestored on a computer-readable storage medium or in a computing system.In some embodiments, these software modules may configure a computingsystem to perform one or more of the exemplary embodiments disclosedherein.

In addition, one or more of the modules described herein may transformdata, physical devices, and/or representations of physical devices fromone form to another. For example, one or more of the modules recitedherein may transform a computing system into a system for providingbackup interfaces. As another example, one or more of the modulesrecited herein may transform a display device into a backup systeminterface.

The preceding description has been provided to enable others skilled inthe art to best utilize various aspects of the exemplary embodimentsdisclosed herein. This exemplary description is not intended to beexhaustive or to be limited to any precise form disclosed. Manymodifications and variations are possible without departing from thespirit and scope of the instant disclosure. The embodiments disclosedherein should be considered in all respects illustrative and notrestrictive. Reference should be made to the appended claims and theirequivalents in determining the scope of the instant disclosure.

Unless otherwise noted, the terms “a” or “an,” as used in thespecification and claims, are to be construed as meaning “at least oneof.” In addition, for ease of use, the words “including” and “having,”as used in the specification and claims, are interchangeable with andhave the same meaning as the word “comprising.”

What is claimed is:
 1. A computer-implemented method for providing backup interfaces, at least a portion of the method being performed by a computing device comprising at least one processor, the method comprising: identifying a backup policy configured to back up data from a source system during a plurality of backup stages according to a backup configuration, wherein at least one backup operation is performed at each backup stage within the plurality of backup stages; identifying a request to display the backup policy within a graphical user interface; and in response to the request, portraying the backup policy within the graphical user interface as a flow diagram, the flow diagram comprising: a box representing the source system that displays an identifier of the source system; a plurality of boxes representing the plurality of backup stages of the backup policy, each box within the plurality of boxes: representing a backup stage within the plurality of backup stages; and displaying an identifier of at least one backup operation performed at the backup stage; a first directed edge connecting the box representing the source system and a first box within the plurality of boxes that indicates that a backup operation performed at the backup stage represented by the first box will be performed on the data from the source system; and a second directed edge connecting the first box with a second box within the plurality of boxes that indicates that: a backup operation performed at the backup stage represented by the second box will be performed on data created by the backup operation performed at the backup stage represented by the first box; and configuration details of the backup operation performed at the backup stage represented by the second box are automatically populated in response to modifications made via the first box to related configuration details of the backup operation performed at the backup stage represented by the first box.
 2. The computer-implemented method of claim 1, wherein the box representing the source system further displays at least one identified selection of data to back up from the source system according to the backup policy.
 3. The computer-implemented method of claim 1, wherein: the configuration details of the backup operation performed at the backup stage represented by the first box comprise at least one of: a storage target of the backup operation performed at the backup stage represented by the first box; and a backup schedule of the backup operation performed at the backup stage represented by the first box; the configuration details of the backup operation performed at the backup stage represented by the second box comprises at least one of: a storage source of the backup operation performed at the backup stage represented by the second box; and a backup schedule of the backup operation performed at the backup stage represented by the second box.
 4. The computer-implemented method of claim 1, wherein the second directed edge comprises an arrow pointing from the first box to the second box.
 5. The computer-implemented method of claim 1, wherein at least one box within the plurality of boxes comprises at least one interface element for modifying at least one configuration detail of a backup operation performed at the backup stage represented by the at least one box within the plurality of boxes.
 6. The computer-implemented method of claim 1, wherein at least one box within the plurality of boxes: displays at least one configuration detail of the backup operation performed at the backup stage represented by the at least one box within the plurality of boxes; comprises at least one interface element for modifying the configuration detail of the backup operation performed at the backup stage represented by the at least one box within the plurality of boxes.
 7. The computer-implemented method of claim 1, wherein: the plurality of backup stages comprise: a first backup stage at which a first backup operation is applied to the data from the source system; and a second backup stage at which a second backup operation is applied to the data created at the first backup stage; the first box represents the first backup stage; and the second box represents the second backup stage; the first directed edge indicates a sequence beginning with the box representing the source system and progressing to the first box; and the second directed edge indicates a sequence beginning with the first box and progressing to the second box.
 8. The computer-implemented method of claim 7, wherein: the plurality of backup stages further comprise a third backup stage at which a third backup operation is applied to the data created at the first backup stage; the plurality of boxes further comprise a third box representing the third backup stage; and the flow diagram further comprises a third directed edge connecting the first box and the third box, the third directed edge indicating a sequence beginning with the first box and progressing to the third box.
 9. The computer-implemented method of claim 1, wherein at least one box within the plurality of boxes comprises an interface element for adding an additional backup stage to the backup policy, the additional backup stage being applied to data created at the backup stage represented by the box within the plurality of boxes.
 10. The computer-implemented method of claim 9, further comprising: receiving an input via the interface element; in response to the input: adding the additional backup stage to the backup policy; and modifying the flow diagram to comprise: an additional box representing the additional backup stage; and an additional directed edge connecting the box within the plurality of boxes and the additional box, the additional directed edge indicating a sequence beginning with the box within the plurality of boxes and progressing to the additional box; and displaying the modified flow diagram within the graphical user interface.
 11. A system for providing backup interfaces, the system comprising: an identification module programmed to: identify a backup policy configured to back up data from a source system during a plurality of backup stages according to a backup configuration, wherein at least one backup operation is performed at each backup stage within the plurality of backup stages; identify a request to display the backup policy within a graphical user interface; an interface module programmed to, in response to the request, portray the backup policy within the graphical user interface as a flow diagram, the flow diagram comprising: a box representing the source system that displays an identifier of the source system; a plurality of boxes representing the plurality of backup stages of the backup policy, each box within the plurality of boxes: representing a backup stage within the plurality of backup stages; and displaying an identifier of at least one backup operation performed at the backup stage; a first directed edge connecting the box representing the source system and a first box within the plurality of boxes that indicates that a backup operation performed at the backup stage represented by the first box will be performed on the data from the source system; and a second directed edge connecting the first box with a second box within the plurality of boxes that indicates that: a backup operation performed at the backup stage represented by the second box will be performed on data created by the backup operation performed at the backup stage represented by the first box; and configuration details of the backup operation performed at the backup stage represented by the second box are automatically populated in response to modifications made via the first box to related configuration details of the backup operation performed at the backup stage represented by the first box; and at least one processor configured to execute the identification module and the interface module.
 12. The system of claim 11, wherein the box representing the source system further displays at least one identified selection of data to back up from the source system according to the backup policy.
 13. The system of claim 11, wherein: the configuration details of the backup operation performed at the backup stage represented by the first box comprise at least one of: a storage target of the backup operation performed at the backup stage represented by the first box; and a backup schedule of the backup operation performed at the backup stage represented by the first box; the configuration details of the backup operation performed at the backup stage represented by the second box comprises at least one of: a storage source of the backup operation performed at the backup stage represented by the second box; and a backup schedule of the backup operation performed at the backup stage represented by the second box.
 14. The system of claim 11, wherein the second directed edge comprises an arrow pointing from the first box to the second box.
 15. The system of claim 11, wherein at least one box within the plurality of boxes comprises at least one interface element for modifying at least one configuration detail of a backup operation performed at the backup stage represented by the at least one box within the plurality of boxes.
 16. The system of claim 11, wherein at least one box within the plurality of boxes: displays at least one configuration detail of the backup operation performed at the backup stage represented by the at least one box within the plurality of boxes; comprises at least one interface element for modifying the configuration detail of the backup operation performed at the backup stage represented by the at least one box within the plurality of boxes.
 17. The system of claim 11, wherein: the plurality of backup stages comprise: a first backup stage at which a first backup operation is applied to the source system; and a second backup stage at which a second backup operation is applied to data created at the first backup stage; the first box represents the first backup stage; and the second box represents the second backup stage; the first directed edge indicates a sequence beginning with the box representing the source system and progressing to the first box; and the second directed edge indicates a sequence beginning with the first box and progressing to the second box.
 18. The system of claim 17, wherein: the plurality of backup stages further comprise a third backup stage at which a third backup operation is applied to the data created at the first backup stage; the plurality of boxes further comprise a third box representing the third backup stage; and the flow diagram further comprises a third directed edge connecting the first box and the third box, the third directed edge indicating a sequence beginning with the first box and progressing to the third box.
 19. The system of claim 11, wherein at least one box within the plurality of boxes comprises an interface element for adding an additional backup stage to the backup policy, the additional backup stage being applied to data created at the backup stage represented by the box within the plurality of boxes.
 20. A non-transitory computer-readable-storage medium comprising one or more computer-executable instructions that, when executed by at least one processor of a computing device, cause the computing device to: identify a backup policy configured to back up data from a source system during a plurality of backup stages according to a backup configuration, wherein at least one backup operation is performed at each backup stage within the plurality of backup stages; identify a request to display the backup policy within a graphical user interface; and in response to the request, portray the backup policy within the graphical user interface as a flow diagram, the flow diagram comprising: a box representing the source system that displays an identifier of the source system; a plurality of boxes representing the plurality of backup stages of the backup policy, each box within the plurality of boxes: representing a backup stage within the plurality of backup stages; and displaying an identifier of at least one backup operation performed at the backup stage; a first directed edge connecting the box representing the source system and a first box within the plurality of boxes that indicates that a backup operation performed at the backup stage represented by the first box will be performed on the data from the source system; and a second directed edge connecting the first box with a second box within the plurality of boxes that indicates that: a backup operation performed at the backup stage represented by the second box will be performed on data created by the backup operation performed at the backup stage represented by the first box; and configuration details of the backup operation performed at the backup stage represented by the second box are automatically populated in response to modifications made via the first box to related configuration details of the backup operation performed at the backup stage represented by the first box. 